Systems and methods for commissioning a security system

ABSTRACT

Systems and methods are provided that can include receiving a plurality of cause and effect rules for a security system that protects a secured area, simulating a plurality of cause and effect rules responsive to user input identifying an emergency event in one of a plurality of zones of the secured area, and during simulation, displaying on a graphical user interface a first indicator that identifies a first output of a first of the plurality of cause and effect rules within a first of the plurality of zones.

PRIORITY INFORMATION

This application is a Continuation of U.S. application Ser. No.16/371,455, filed Apr. 1, 2019, the contents of which are incorporatedherein by reference.

FIELD

The present invention relates generally to security systems. Moreparticularly, the present invention relates to systems and methods forcommissioning a security system.

BACKGROUND

Security systems are known to detect threats within a secured area, andsuch threats can include events that represent a risk to human safety ora risk to assets.

Security systems typically include one or more security sensors thatdetect the threats within the secured area. For example, smoke, motion,and/or intrusion sensors can be distributed throughout the secured areain order to detect the threats. Furthermore, security systems typicallyinclude notification appliances, such as sounders and strobe lights, tonotify occupants of an emergency.

Commissioning a security system is very laborious and time-consuming.For example, known systems and methods for commissioning securitysystems involve a commissioning engineer (CE) manually creating rulesand manually entering multi-line configuration data into a table or aspreadsheet. As such, there is a need for simpler and faster systems andmethods for commissioning security systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system in accordance with disclosedembodiments;

FIG. 2 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 3 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 4 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 5 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 6 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 7 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 8 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 9 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 10 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 11 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 12 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 13 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 14 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 15 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 16 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 17 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 18 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 19 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 20 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 21 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 22 is a floor plan with a plurality of zones in accordance withdisclosed embodiments;

FIG. 23 is a table of zone distance factors for a plurality of zones ina floor plan in accordance with disclosed embodiments;

FIG. 24 is a table of alert sequence factors for a plurality of zones ina floor plan in accordance with disclosed embodiments;

FIG. 25 is a flow diagram of a method in accordance with disclosedembodiments;

FIG. 26 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments;

FIG. 27 is a graphical user interface displayed on a user terminal inaccordance with disclosed embodiments; and

FIG. 28 is a flow diagram of a method in accordance with disclosedembodiments.

DETAILED DESCRIPTION

While this invention is susceptible of an embodiment in many differentforms, there are shown in the drawings and will be described herein indetail specific embodiments thereof with the understanding that thepresent disclosure is to be considered as an exemplification of theprinciples of the invention. It is not intended to limit the inventionto the specific illustrated embodiments.

Embodiments disclosed herein can include systems and methods forcommissioning a security system and automatically defining, creating,and generating cause and effect rules for the security system. Forexample, systems and methods disclosed herein can display a graphicaluser interface (GUI) on a user terminal, such as a personal computer, atablet, or a smartphone, with a floor plan of a secured area monitoredby the security system and can receive user input via the floor plandisplayed on the GUI for defining and identifying a plurality of zonesof the secured area, drawing or otherwise identifying a respectiveevacuation route from each of the plurality of zones, customizingchanges to the cause and effect rules via graphically-displayed widgets,and graphically simulating the cause and effect rules as customized,results of which can be displayed on the GUI.

In some embodiments, responsive to receiving user input, systems andmethods disclosed herein can automatically define, create, and generatethe cause and effect rules. For example, the user input can define andidentify respective boundaries of each of the plurality of zones drawnon the floor plan and can identify the respective evacuation route fromeach of the plurality of zones drawn on the floor plan. In someembodiments, systems and methods disclosed herein can retrieve buildingdata stored in a building information model (BIM) file of the securedarea, which can be stored in a computer-readable memory, to identifyrespective distances between each of the plurality of zones andemergency exits in the secured area, and in some embodiments, the BIMfile can include an industrial foundation classes (IFC) file withstructural data about the secured area, such as locations of walls,doors, and the emergency exits. Accordingly, in some embodiments, thefloor plan can be generated from the building data retrieved from theBIM file.

After automatically defining, creating, and generating the cause andeffect rules, systems and methods disclosed herein can receive userinput with instructions to simulate the cause and effect rules, and insome embodiments, the cause and effect rules can be simulatedgraphically via the GUI. For example, during simulation, activatedalarms in some of the plurality of zones can flash or change color onthe floor plan, and the GUI can display alarm and alert notifications inreal-time to correspond with output of the cause and effect rules.

FIG. 1 is a block diagram of a security system 10 in accordance withdisclosed embodiments. As seen in FIG. 1, the security system 10 caninclude one or more security sensors 12, 14 that can monitor a securedarea 16 for threats, and in some embodiments, the security sensors 12,14 can include intrusion, camera, motion, fire, smoke, and gasdetectors. The security sensors 12, 14 can communicate with a controlpanel 18, and the control panel 18 can monitor for activation of thesecurity sensors 12, 14.

In some embodiments, the control panel 18 may send an alarm message to acentral monitoring station 20 upon the activation of one of the securitysensors 12, 14, and the central monitoring station 20 can respond bysummoning the appropriate help. For example, if the one of the securitysensors 12, 14 detects a fire, then the central monitoring station 20may summon a local fire department. Alternatively, if the one of thesecurity sensors 12, 14 detects an intrusion, then the centralmonitoring station 20 may summon the police. Additionally, the controlpanel 18 can send an activation message to one or more alarmnotification devices 20, 22, and the alarm notification devices 20, 22can activate a visual or audible alarm to notify occupants of thesecured area 16 about the threats.

The control panel 18 can also communicate with a user terminal 24, andthe user terminal 24 can implement, store, and execute software that candisplay a GUI on a user interface device 34 or other display of the userterminal 24 to assist a CE in commissioning the security system 10. Theuser interface device 34 can include a keyboard, a mouse, or atouchscreen that can receive user input that the user terminal 24 canuse to define, create, and generate cause and effect rules for thesecurity system 10. Then, the user terminal 24 can transmit the causeand effect rules to the control panel 18, and the control panel canfunction in accordance with the cause and effect rules.

The user terminal 24 can include control circuitry 32, which can includea programmable processor 32 a and executable control software 32 b aswould be understood by one of ordinary skill in the art. The executablecontrol software 32 b can be stored on a transitory or non-transitorycomputer readable medium, including, but not limited to local computermemory, RAM, optical storage media, magnetic storage media, and thelike. In some embodiments, the control circuitry 32, the programmableprocessor 32 a, and the executable control software 32 b can execute andcontrol some of the methods disclosed herein, such as, for example,displaying the GUI, receiving user input to define the cause and effectrules, and, responsive thereto, creating and generating the cause andeffect rules.

FIG. 2 is a GUI 200 that can be displayed on the user interface device34 of the user terminal 24 as part of commissioning the security system10 in accordance disclosed embodiments. In some embodiments, systems andmethods disclosed herein can retrieve a BIM file from a memory device toidentify information to be displayed in the GUI 200.

First, the GUI 200 can receive user input to define and identify aplurality of zones 202 of the secured area 16 monitored by the securitysystem 10. For example, the GUI 200 can display an add zone button 204,and responsive to the GUI 200 receiving user input of the CE selectingthe add zone button 204, systems and methods disclosed herein canidentify a new one of the plurality of zones 202 and identify the newone of the plurality of zones 202 with a name identified by the userinput. Then, the GUI 200 can receive user input with instructions fromthe CE to add security system devices 12, 14, 20, or 22 to the new oneof the plurality of zones 202. For example, the GUI 200 can display adevice area 206 that can receive user input of the CE identifying namesfor the security system devices 12, 14, 20, or 22, and responsivethereto, the GUI 200 can display respective information for each of thesecurity system devices 12, 14, 20, or 22, such as a respective status,a respective serial number, a respective manufacturing date, andrespective events detected by a respective one of the security systemdevices 12, 14, 20, or 22. Finally, the GUI 200 can display an activatedevice button 208, and responsive to the GUI 200 receiving user input ofthe CE selecting the activate device button 208 for a selected one ofthe security system devices 12, 14, 20, or 22, systems and methodsdisclosed herein can activate the selected one of the security systemdevices 12, 14, 20, or 22.

After identifying the new one of the plurality of zones 202 responsiveto the GUI 200 receiving user input, systems and methods disclosedherein can display a floor plan 310 of the secured area 16 to define thenew one of the plurality of zone 202. For example, FIG. 3 is a GUI 300that can be displayed on the user interface device 34 of the userterminal 24 in accordance with disclosed embodiments. In someembodiments, systems and methods disclosed herein can process buildingdata from the BIM file to generate and display the floor plan 310. Asseen, the GUI 300 can display a mark zones button 312, and responsive tothe GUI 300 receiving user input of the CE selecting the mark zonesbutton 312 and selecting the new one of the plurality of zones 202(“West Wing Conference”), systems and methods disclosed herein canreceive user input defining metes and bounds of the new one of theplurality of zones 202.

For example, FIG. 4 is a GUI 400 that can be displayed on the userinterface device 34 of the user terminal. As seen, the GUI 400 candisplay a zone drawing tool button 414, and responsive to the GUI 400receiving user input of the CE selecting the zone drawing tool button414, systems and methods disclosed herein can receive user input of theCE defining the metes and bounds of the new one of the plurality ofzones 202. For example, the GUI 400 can receive an identification of anoutline of a drawn zone 416 on the floor plan or an identification of ashape (e.g. a rectangle) for the drawn zone 416. Then, systems andmethods disclosed herein can associate BIM coordinates of the drawn zone416 with the new one of the plurality of zones 202.

After identifying the new one of the plurality of zones 202 andassigning security system devices to the new one of the plurality ofzones 202 responsive to the GUI 200 receiving user input and definingthe metes and bounds of the new one of the plurality of zones 202 viathe GUI 300 and the GUI 400 receiving user input, systems and methodsdisclosed herein can define the cause and effect rules for the securitysystem 10 either manually using configurable widgets or automaticallyusing drawn evacuation routes. FIGS. 5-19 are GUIs that can be displayedon the user interface device 34 of the user terminal 24 for manuallydefining the cause and effect rules with the configurable widgets, andFIGS. 20-21 are GUIs that can be displayed on the user interface 34 ofthe user terminal 24 for automatically defining the cause and effectrules with the drawn evacuation routes.

For example, as seen in FIG. 5, systems and methods disclosed herein candisplay a GUI 500 when none of the cause and effect rules have beendefined, and the GUI 500 can display an apply template button 518, animport from excel button 520, and a create rules button 522. Responsiveto the GUI 500 receiving user input of the CE selecting the applytemplate button 518, systems and method disclosed herein can retrievepreviously saved templates saved in the memory device. Additionally oralternatively, responsive to the GUI 500 receiving user input of the CEselecting the import from excel button 520, systems and methodsdisclosed herein can retrieve a spreadsheet (e.g. .xls, .csv) saved inthe memory device and convert the cause and effect rules in thespreadsheet into widgets for display.

Additionally or alternatively, responsive to the GUI 500 receiving userinput of the CE selecting the create rules button 522, systems andmethods disclosed herein can display a GUI 600 as seen in FIG. 6. TheGUI 600 can display a rule name box 624, a rule description box 626, andan input selection area 628. Responsive to the GUI 600 receiving userinput of the CE selecting the rule name box 624, systems and methodsdisclosed herein can identify a rule name for a new one of the cause andeffect rules. Responsive to the GUI 600 receiving user input of the CEselecting the rule description box 626, systems and methods disclosedherein can associate a description identified by the user input with thenew one of the cause and effect rules.

Responsive to the GUI 600 receiving user input of the CE selecting theinput selection area 628, the GUI 600 can display an input selectionpop-up window 730 that includes input menu selections 732 displayedtherein as seen in FIG. 7. Responsive to the GUI 600 receiving userinput of the CE selecting one or more of the input menu selections 732,systems and methods disclosed herein can identify a correspondingplurality of events and triggers as input for the new one of the causeand effect rules. For example, the input can include any sensordetecting any alarm condition in an identified zone, any sensordetecting any alarm condition in any zone in alarm, an identified groupof sensors detecting any alarm condition, sensors in an identified loopdetecting any alarm condition, an identified sensor detecting any alarmcondition, or any sensor detecting any alarm condition in an identifiedarea.

Responsive to the GUI 600 receiving user input of the CE selecting anyof the input menu selections 732 (e.g. “Zone”), the GUI 600 can displaythe input selection pop-up window 730 with a list of zones 834 thatincludes the new one of the plurality of zones 202, a search bar 938,and a selection button 940 displayed therein as seen in FIG. 8 and inFIG. 9. Responsive to the GUI 600 receiving user input of the CEselecting a selected zone 936 (“Server Room West Wing”) from the list ofzones 834, systems and methods disclosed herein can identify theselected zone 936. Additionally or alternatively, responsive to the GUI600 receiving user input of the CE entering text into the search bar938, systems and methods disclosed herein can assist the CE in selectingthe selected zone 936 from the list of zones 834, for example, bydisplaying entries in the list of zones 834 that match the text enteredinto the search bar 938. It is to be understood that systems and methodsdisclosed herein can identify more than one entry on the list of zones834.

Responsive to the GUI 600 receiving user input of the CE selecting theselection button 940, the GUI 600 can display an input widget 1042, aninput selection area 1044, and a condition selection area 1046 as seenin FIG. 10. The input widget 1042 can display identifying informationabout the input selected for the new one of the cause and effect rules,such as a type of the input selected for the new one of the cause andeffect rules, any of the plurality of zones associated with the inputselected for the new one of the cause and effect rules, device(s)associated with the input selected for the new one of the cause andeffect rules, a number of the devices in the plurality of zonesassociated with the input selected for the new one of the cause andeffect rules, etc. Responsive to the GUI 600 receiving user input of theCE selecting the input selection area 1044 and identifying additionalitems for the input for the new one of the cause and effect rules,systems and methods disclosed herein can identify the additional itemsfor the input for the new one of the cause and effect rules.

Responsive to the GUI 600 receiving user input of the CE selecting thecondition selection area 1046, the GUI 600 can display a conditionselection pop-up window 1148 with a plurality of conditions 1150, asearch bar, and a selection button 1254 displayed therein as seen inFIGS. 11 and 12. Responsive to the GUI 600 receiving user input of theCE selecting one or more of the plurality of conditions 1150, systemsand methods disclosed herein can identify the plurality of conditions1150 selected as conditions for the new one of the cause and effectrules. For example, the conditions can include any sensor detecting anyalarm, any sensor detecting any pre-alarm, any sensor detecting anyalarm progression, or any sensor detecting any fault. It is to beunderstood that systems and methods disclosed herein can identify morethan one of the plurality of conditions 1150 as the conditions for thenew one of the cause and effect rules.

Responsive to the GUI 600 receiving user input of the CE selecting anyof the plurality of conditions 1150 (e.g. “Alarm Progression” 1252) andthe selection button 1254, the GUI 600 can display a condition widget1356, a condition selection area 1358, and an output selection area 1360as seen in FIG. 13. The condition widget 1356 can display identifyinginformation about the conditions selected for the new one of the causeand effect rules, such as a type of the conditions selected, an alarminterval time for the conditions selected, etc. Responsive to the GUI600 receiving user input of the CE selecting the condition selectionarea 1358 and identifying additional items for the conditions selectedfrom the new one of the cause and effect rules, systems and methodsdisclosed herein can identify the additional items for the conditionsfor the new one of the cause and effect rules.

Responsive to the GUI 600 receiving user input of the CE selecting theoutput selection area 1360 to define output of the new one of the causeand effect rules, the GUI 600 can display an output selection pop-upwindow 1462 with a plurality of outputs 1464, a search bar, and aselection button 1568 displayed therein as seen in FIGS. 14-16.Responsive to the GUI 600 receiving user input of the CE selecting oneor more of the plurality of outputs 1464 (“Activate Sounders” 1566),systems and methods disclosed herein can identify the plurality ofoutputs selected as the output for the new one of the cause and effectrules. For example, the output can include activating sounders,activating gas suppression, activating strobe lights, etc. It is to beunderstood that systems and methods disclosed herein can identify morethan one of the plurality of outputs 1464 (e.g. “Activate Sounders” and“Activate Gas Suppression”) to be the output for the new one of thecause and effect rules.

Responsive to the GUI 600 receiving user input of the CE selecting theselection button 1568, the GUI 600 can display output widget(s) 1770 asseen in FIG. 17 and FIG. 18. It is to be understood that a number of theoutput widgets 1770 displayed can equal a number of the plurality ofoutputs 1464 identified for the new one of the cause and effect rules.The output widget(s) 1770 can display identifying information about theoutput identified for the new one of the cause and effect rules, such asa type of the output selected for the new one of the cause and effectrules, an output delay time for the output selected for the new one ofthe cause and effect rules, etc.

Furthermore, when more than one of the plurality of outputs 1464 isidentified for the new one of the cause and effect rules, systems andmethods disclosed herein can automatically activate and display alogical connection widget 1774 on the GUI 600. Responsive to the GUI 600receiving user input of the CE setting the logical connection widget1774 to “AND” as in FIG. 17 and the input and the conditions for the newone of the cause and effect rules being met, systems and methodsdisclosed herein can execute a logical AND on the output widget(s) 1770displayed, thereby activating the output for all of the output widgets1770 displayed. However, responsive to the GUI 600 receiving user inputof the CE setting the logical connection widget 1774 to “OR” as in FIG.18 and the input and the conditions for the new one of the cause andeffect rules being met, systems and methods disclosed herein can executea logical OR on the output widget(s) 1770 displayed.

After systems and methods disclosed herein identify the input, theconditions, and the output to define the new one of the cause and effectrules, the GUI 600 can display a create rule button 1876 for selectionthereof. Responsive to the GUI 600 receiving user input of the CEselecting the create rule button 1876, systems and methods disclosedherein can save the new one of the cause and effect rules and display asuccessful rule creation banner 1978 as seen in FIG. 19 indicating thatthe new one of the cause and effect rules has successfully been created.

As explained above, the cause and effect rules can also be automaticallydefined. For example, in some embodiments, systems and methods disclosedherein can automatically define the cause and effect rules responsive toreceiving user input of the CE identifying the plurality of zones 202 orretrieving an identification of the plurality of zones from the BIM fileand responsive to receiving user input of the drawn evacuation routes.

After identifying the new one of the plurality of zones 202 responsiveto the GUI 200 receiving user input and defining the metes and bounds ofthe new one of the plurality of zones 202 responsive to the GUI 300 andthe GUI 400 receiving user input, systems and methods disclosed hereincan display a GUI 2000 that includes a list of the plurality of zones202 created, the floor plan 310, and a draw evacuation route button 2080as seen in FIG. 20. Responsive to the GUI 2000 receiving user input ofthe CE selecting the draw evacuation route button 2080, the GUI 200 canreceive user input of the CE drawing or otherwise identifying anevacuation route 2082 on the floor plan 310.

For example, as seen in FIG. 20, the evacuation route 2082 can startfrom a first of the plurality of zones 202 displayed on the floor plan310 and can end at an emergency exit 2084 displayed on the floor plan310. In some embodiments, the evacuation route 2082 can include adirection parameter to the emergency exit 2084, and in some embodiments,systems and methods disclosed herein can use coordinate data from theBIM file to identify a distance from the first of the plurality of zones202 to the emergency exit 2084.

Additionally or alternatively, after identifying the new one of theplurality of zones 202 responsive to the GUI 200 receiving user inputand identifying the metes and bounds of the new one of the plurality ofzones 202 via the GUI 300 and the GUI 400 receiving user input, systemsand methods disclosed herein can display a GUI 2100 that includes a gridview of the BIM file. For example, in some embodiments, the grid viewmay omit floor plan details, such as wall and door locations, and onlydisplay the plurality of zones 202.

As seen in FIG. 21, exemplary evacuation routes 2188, 2192 can extendthrough, that is, touch, or abut one or more of the plurality of zones202. For example, in the grid view 2186 of a ground floor, one of theevacuation routes 2188 can begin in zone 007 and extend through zones010, 004, and 008. Accordingly, systems and methods disclosed herein canidentify the one of the evacuation routes 2188 as applying to zones 010,004, and 008 and can display a notification on the GUI 2100 indicatingthat zones 005 and 006 are not associated with any of the evacuationroutes. As another example, in the grid view 2190 of a first floor, oneof the evacuation routes 2192 can begin in zone 010 and extend throughzones 010, 004, and 008. Accordingly, systems and methods disclosedherein can identify the one of the evacuation routes 2192 as applying tozones 005, 006, and 007.

Responsive to receiving user input of the CE identifying the evacuationroutes, systems and methods disclosed herein can automatically definethe cause and effect rules as disclosed herein, and in some embodiments,the GUI 2100 can display the cause and effect rules a cause and effectrule area 2194.

FIG. 22 is an exemplary floor plan 2200 of zones in a secured area andcan be used to illustrate systems and methods disclosed hereinautomatically defining the cause and effect rules. As seen in FIG. 22,the floor plan 2200 can include sixteen zones (zone 1-zone 16) and twoemergency exits 2202, 2204. Any GUI displaying the floor plan 2200 canreceive user input of the CE drawing or otherwise identifying twoevacuation routes 2206, 2208. As seen, zones 1-8 can follow a first ofthe evacuation routes 2206 to a first of the emergency exits 2202, andzones 9-16 can follow a second of the evacuation routes 2208 to a secondof the emergency exits 2204.

Responsive to receiving user input of the CE drawing or otherwiseidentifying the evacuation routes 2206, 2008, systems and methodsdisclosed herein can identify a respective distance factor from each ofthe zones to an assigned one of the emergency exits 2202, 2204 based onan assigned one of the evacuation routes 2206, 2008 for a respective oneof the plurality of zones. For example, the respective distance factorfrom zone 1 to the first of the emergency exits 2202 can be one becauseone of the zones stands between zone 1 and the first of the emergencyexits 2202 (e.g. zone 1). Similarly, the respective distance factor fromzone 8 to the first of the emergency exits 2202 can be four because fourof the zones stand between zone 8 and the first of the emergency exits2202 (e.g. zones 2, 4, 6, and 8). As an alternative example, therespective distance factor from zone 16 to the second of the emergencyexits 2204 can be one because one of the zones stands between zone 16and the second of the emergency exits 2204 (e.g. zone 16). However, ifzone 16 been assigned an evacuation route that ended at the first of theemergency exits 2202, then the respective distance factor from zone 16to the first of the emergency exits 2202 would have been eight becauseeight of the zones stand between zone 16 and the first of the emergencyexits 2202 (e.g. zones 2, 4, 6, 8, 10, 12, 14, 16).

While the respective distance factor from each of the zones to theassigned one of the emergency exits 2202, 2204 are shown in integer formfor illustration purposes, systems and methods disclosed herein can alsouse the BIM coordinates to identify the respective distance factor fromeach of the zones to the assigned one of the emergency exits 2202, 2204in actual distance form, such as a respective straight line distance(e.g. “as the crow flies”) or a respective distance traveled via theassigned one of the evacuation routes 2206, 2008.

In any embodiment, systems and methods disclosed herein can store therespective distance factor from each of the zones to the assigned one ofthe emergency exits 2202, 2204 in a table in the memory device. In thisregard, FIG. 23 is a table 2300 of zone distance factors for from thezones to the assigned emergency exits 2202, 2204 in the floor plan 2200of FIG. 22.

As seen in FIG. 22, systems and methods disclosed herein can receiveuser input of the CE identifying an emergency event (simulated or real)in one or more of the zones, for example, in zones 3 and 4, therebymaking zones 3 and 4 emergency ones of the zones. Responsive toidentifying the emergency event, systems and methods disclosed hereincan identify a respective relative distance from each of the zones tothe emergency ones of the zones. For example, systems and methodsdisclosed herein can identify the respective relative distance from eachof the emergency ones of the zones, zones 3 and 4, to be zero. However,systems and methods disclosed herein can identify the respectiverelative distance from each of zones 1, 2, 5, and 6 to the emergencyones of the zones to be one because each of zones 1, 2, 5, and 6 isimmediately adjacent to the emergency ones of the zones.

In this regard, FIG. 24 is a table 2400 of alert sequence factors forthe zones in the floor plan 2200 of FIG. 22. As seen, the third columnof the table 2400 identifies the respective distance factor from each ofthe zones to the assigned one of the emergency exits 2202, 2204, and thefourth column of the table 2400 identifies the respective relativedistance from each of the zones to the emergency ones of the zones,zones 3 and 4. In some embodiments, systems and methods disclosed hereincan identify the respective distance factor from each of the zones tothe assigned one of the emergency exits 2202, 2204 and the respectiverelative distance from each of the zones to the emergency ones of thezones prior to or during simulation of the emergency event.

Then, systems and methods disclosed herein can multiply the respectivedistance factor by the respective relative distance for each of thezones to identify a respective alert sequence factor, which isidentified in the fifth column of the table 2400. Finally, systems andmethods disclosed herein can automatically define the cause and effectrules based on the respective alert sequence factor for each of thezones.

For example, the cause and effect rules can generate an alarmnotification in any zones in which the emergency event is detected (e.g.alert sequence factor=0) and can generate alert evacuation notificationsin descending order from a highest alert sequence factor for each of thezones assigned to the one of the emergency exits 2202 to which the zonesin which the emergency events are detected are assigned to a lowest,non-zero alert sequence factor for each of the zones assigned to the oneof the emergency exits 2202 to which the zones in which the emergencyevents are detected are assigned. That is, systems and methods disclosedherein can first generate one of the alert evacuation notifications inzones 7 and 8 because, like zones 3 and 4, zones 7 and 8 are assigned tothe first one of the emergency exits 2202 and have the highest alertsequence factor for each of the zones assigned to the first one of theemergency exits 2202. Indeed, zones 7 and 8 have the highest alertsequence factor for each of the zones assigned to the first one of theemergency exits 2202 because, of those zones, zones 7 and 8 are locatedfurthest from the first of the emergency exits 2202 and, therefore,require the most time for evacuation therefrom. Next, systems andmethods disclosed herein can generate one of the alert evacuationnotifications in zones 5 and 6 because, like zones 3 and 4, zones 5 and6 are assigned to the first one of the emergency exits 2202 and have anext highest alert sequence factor for each of the zones assigned to thefirst one of the emergency exits 2202. Indeed, after zones 7 and 8,zones 5 and 6 have the next highest alert sequence factor for each ofthe zones assigned to the first one of the emergency exits 2202 because,of those zones, zones 5 and 6 are located the next furthest from thefirst of the emergency exits 2202. Finally, systems and methodsdisclosed herein can generate one of the alert evacuation notificationsin zones 1 and 2 because, like zones 3 and 4, zones 1 and 2 are assignedto the first one of the emergency exits 2202 and have the lowest,non-zero alert sequence for each of the zones assigned to the first oneof the emergency exits. Indeed, zones 1 and 2 have the lowest, non-zeroalert sequence factor for each of the zones assigned to the first one ofthe emergency exits 2202 because, of those zones, zones 1 and 2 arelocated the closest to the first of the emergency exits 2202. In someembodiments, systems and methods disclosed herein can implement a delay(e.g. 30 seconds) between alerting each of the zones.

As seen in FIG. 22, zones 9-16 can be assigned to the second of theemergency exits 2204. However, when the emergency event is detected inany of the zones assigned to the first of the emergency exits 2202,systems and methods disclosed herein executing the cause and effectrules can generate alert information notifications in each of the zonesassigned to the second of the emergency exits 2202, zones 9-16.

In some embodiments, the cause and effect rules can include time delays.Accordingly, systems and methods disclosed herein can separate the alarmnotification, the alert evacuation notifications, and the alertinformation notifications in time and/or delay the alarm notifications,the alert evacuation notifications, and the alert informationnotifications. For example, systems and methods disclosed herein canactivate the alarm notification immediately after identifying theemergency event in the emergency ones of the zones. Then, systems andmethods disclosed herein can activate a first of the alert evacuationnotifications a predetermined period of time after the alarmnotification, activate a second of the alert evacuation notificationsthe predetermined period of time after the first of the alerts, activatea third of the alert evacuation notifications the predetermined periodof time after the second of the alerts, and activate the alertinformation notifications the predetermined period of time after thethird of the alert evacuation notifications.

It is to be understood that systems and methods disclosed herein canautomatically define the cause and effect rules for any and all of thezones in which the emergency event is identified.

FIG. 25 is flow diagram of a method 2500 in accordance with disclosedembodiments. As seen in FIG. 25, the method 2500 can include a processor(e.g. the programmable processor 32) receiving input defining andidentifying a respective location of each of a plurality of zones in asecured area as in 2502 and the processor receiving input identifying arespective evacuation route from each of the plurality of zones as in2504. For example, the processor can receive the input defining andidentifying the respective location of each of the plurality of zonesand the input identifying the respective evacuation route from each ofthe plurality of zones via user input entered into a floor plandisplayed on a GUI.

Then, the method 2500 can include the processor identifying an emergencyevent in one of the plurality of zones as in 2506, the processoridentifying a respective distance factor from each of the plurality ofzones to an emergency exit based on the respective evacuation route froma respective one of the plurality of zones as in 2508, the processoridentifying a respective relative distance from each of the plurality ofzones to the one of the plurality of zones in which the emergency eventis identified as in 2510, and the processor identifying a respectivealert sequence factor for each of the plurality of zones by multiplyingthe respective distance factor by the respective relative distance foreach of the plurality of zones as in 2512. The respective alert sequencefactor for each of the plurality of zones can be ordered highest tolowest, and the method 2500 can include the processor generating analarm notification in the one of the plurality of zones in which theemergency event is identified as in 2514 and, for remaining ones of theplurality of zones, the processor generating alert notifications in anorder corresponding to the respective alert sequence factor for theremaining ones of the plurality of zones such that one of the remainingones of the plurality of zones with a highest alert sequence factor canreceive one of the alert notifications before one of the remaining onesof the plurality of zones with a lowest alert sequence factor receivesone of the alert notifications.

After automatically defining the cause and effect rules, systems andmethods disclosed herein may display a GUI 2500 identifying all of thecause and effect rules defined as seen in FIG. 26. As seen, the causeand effect rules in FIG. 26 can be displayed as widgets, which can becustomized pursuant to received user input.

As seen in FIG. 26, the GUI 2500 can also display a simulate button2502, and responsive to the GUI 2500 receiving user input of the CEselecting the simulate button 2502, systems and methods disclosed hereincan simulate the cause and effect rules. For example, in someembodiments, systems and methods disclosed herein can graphicallysimulate the cause and effect rules by displaying a GUI 2700 as seen inFIG. 27.

As seen, the GUI 2700 can include a map or floor plan 2702 that can bedisplayed in different colors. For example, systems and methodsdisclosed herein can display any of the plurality of zones in the floorplan 2702 in a non-white color when systems and methods disclosed hereinactivate the alarm notification or one of the alert notificationstherein. In some embodiments, systems and methods disclosed herein candisplay any of the plurality of zones in the floor plan 2702 in a firstcolor when systems and methods disclosed herein activate the alarmnotification therein and can display any of the plurality of zones in asecond, different color when systems and methods disclosed hereinactivate one of the alert notifications therein. In some embodiments,systems and methods disclosed herein can also display a speaker icon anyof the plurality of zones when systems and methods disclosed hereinactivate the alarm notification therein to represent sounders beingactivated therein. In some embodiments, during the simulation, any ofthe plurality of zones can change color or flash color in real-time tocorrespond with the output of the cause and effect rules.

As seen in FIG. 27, the GUI 2700 can also display cause and effectoutputs in a simulation list 2704, and in some embodiments, during thesimulation, items in the simulation list 2704 can be added thereto fordisplay on the GUI 2700 in real-time to correspond with the output ofthe cause and effect rules.

It is to be understood that systems and methods disclosed herein canexecute a plurality of simulations to simulate a plurality of identifiedevents, such as a fire, carbon monoxide, a burglary, etc., such thateach of the plurality of identified events can originate from arespective one of the plurality of zones. In some embodiments, theplurality of simulations can be displayed on a per floor basis.

FIG. 28 is flow diagram of a method 2800 in accordance with disclosedembodiments. As seen in FIG. 28, the method 2800 can include a processor(e.g. the programmable processor 32) receiving cause and effect rules asin 2802, and the processor receiving user input selecting at least onesimulation parameter (e.g. an identified event), such as a fire event, acarbon monoxide event, a burglary event, or any other emergency event,as in 2804. As disclosed herein, the processor can receive the cause andeffect rules from user input manually entering the cause and effectrules into a GUI or from an automatic generation of the cause and effectrules responsive to user input. Then, the method 2800 can include theprocessor highlighting or flashing a plurality of zones in a floor plandisplayed on a GUI with color in accordance with the cause and effectrules as in 2806 and the processor displaying cause and effect ruleoutputs in a list on the GUI as in 2808. In some embodiments, theprocessor can highlight or flash the plurality of zones with the colorand add the cause and effect rule outputs to the list in real-time tocorrespond with the output of the cause and effect rules, including, forexample, a delay time identified in the cause and effect rules.

Although a few embodiments have been described in detail above, othermodifications are possible. For example, the logic flows described abovedo not require the particular order described or sequential order toachieve desirable results. Other steps may be provided, steps may beeliminated from the described flows, and other components may be addedto or removed from the described systems. Other embodiments may bewithin the scope of the invention.

From the foregoing, it will be observed that numerous variations andmodifications may be effected without departing from the spirit andscope of the invention. It is to be understood that no limitation withrespect to the specific system or method described herein is intended orshould be inferred. It is, of course, intended to cover all suchmodifications as fall within the spirit and scope of the invention.

What is claimed is:
 1. A method comprising: receiving a plurality ofcause and effect rules for a security system that protects a securedarea; responsive to user input identifying an emergency event in one ofa plurality of zones of the secured area, simulating the plurality ofcause and effect rules; and during simulation, displaying on a graphicaluser interface a first indicator that identifies a first output of afirst of the plurality of cause and effect rules within a first of theplurality of zones.
 2. The method of claim 1 further comprising:overlaying the first indicator on a floor plan of the secured areadisplayed on the graphical user interface.
 3. The method of claim 2further comprising: changing a color of the first of the plurality ofzones on the floor plan displayed on the graphical user interface. 4.The method of claim 3 further comprising: flashing the color of thefirst of the plurality of zones on the floor plan displayed on thegraphical user interface.
 5. The method of claim 1 further comprising:displaying text on the graphical user interface explaining the firstoutput of the first of the plurality of cause and effect rules.
 6. Themethod of claim 1 further comprising: during the simulation, displayingon the graphical user interface a second indicator that identifies asecond output of a second of the plurality of cause and effect ruleswithin a second of the plurality of zones.
 7. The method of claim 6further comprising: overlaying the first indicator and the secondindicator on a floor plan of the secured area displayed on the graphicaluser interface.
 8. The method of claim 7 further comprising: displayingthe first indicator and the second indicator in real-time to correspondto activation times of the first output of the first of the plurality ofcause and effect rules and the second output of the second of theplurality of cause and effect rules.
 9. The method of claim 6 furthercomprising: displaying first text on the graphical user interfaceexplaining the first output of the first of the plurality of cause andeffect rules; and displaying second text on the graphical user interfaceexplaining the second output of the second of the plurality of cause andeffect rules.
 10. The method of claim 9 further comprising: displayingthe first text and the second text in real-time to correspond toactivation times of the first output of the first of the plurality ofcause and effect rules and the second output of the second of theplurality of cause and effect rules.
 11. A system comprising: a userinterface device; a programmable processor; and executable controlsoftware stored on a non-transitory computer readable medium, whereinthe user interface device receives or the programmable processor and theexecutable control software retrieve a plurality of cause and effectrules for a security system that protects a secured area, wherein,responsive to user input identifying an emergency event in one of aplurality of zones of the secured area, the programmable processor andthe executable control software simulate the plurality of cause andeffect rules, and wherein, during simulation, the programmable processorand the executable control software instruct the user interface deviceto display a first indicator that identifies a first output of a firstof the plurality of cause and effect rules within a first of theplurality of zones.
 12. The system of claim 11 wherein the programmableprocessor and the executable control software instruct the userinterface device to overlay the first indicator on a floor plan of thesecured area displayed on the user interface device.
 13. The system ofclaim 12 wherein the programmable processor and the executable controlsoftware instruct the user interface device to change a color of thefirst of the plurality of zones on the floor plan displayed on the userinterface device.
 14. The system of claim 13 wherein the programmableprocessor and the executable control software instruct the userinterface device to flash the color of the first of the plurality ofzones on the floor plan displayed on the user interface device.
 15. Thesystem of claim 11 wherein the programmable processor and the executablecontrol software instruct the user interface device to display textexplaining the first output of the first of the plurality of cause andeffect rules.
 16. The system of claim 11 wherein, during the simulation,the programmable processor and the executable control software instructthe user interface device to display a second indicator that identifiesa second output of a second of the plurality of cause and effect ruleswithin a second of the plurality of zones.
 17. The system of claim 16wherein the programmable processor and the executable control softwareinstruct the user interface device to overlay the first indicator andthe second indicator on a floor plan of the secured area displayed onthe user interface device.
 18. The system of claim 17 wherein theprogrammable processor and the executable control software instruct theuser interface device to display the first indicator and the secondindicator in real-time to correspond to activation times of the firstoutput of the first of the plurality of cause and effect rules and thesecond output of the second of the plurality of cause and effect rules.19. The system of claim 16 wherein the programmable processor and theexecutable control software instruct the user interface device todisplay first text explaining the first output of the first of theplurality of cause and effect rules and second text explaining thesecond output of the second of the plurality of cause and effect rules.20. The system of claim 19 wherein the programmable processor and theexecutable control software instruct the user interface device todisplay the first text and the second text in real-time to correspond toactivation times of the first output of the first of the plurality ofcause and effect rules and the second output of the second of theplurality of cause and effect rules.